Companion to objectstack-ai/objectstack#3913 (server fix: objectstack-ai/objectstack#3930). The issue names this side explicitly — "the shipped console does exactly that on its main action path… so global-action failures produce a green success toast".

The hole

useConsoleActionRuntime.serverActionHandler — the console's main action path (list toolbars, row actions, page actions) — decided success from res.ok and the OUTER envelope only:

if (!res.ok || (json && json.success === false)) { /* failure */ }

A server older than objectstack#3913 reports a handler failure as HTTP 200 with the failure nested one level down:

{"success":true,"data":{"success":false,"error":"Action 'log_call' on object '*' not found"}}

Both guards pass. The action was reported as completed: the ActionRunner fired its green "completed" toast, the list refreshed, and the real error was swallowed.

RecordDetailView's copy of the same handler already inspected the inner envelope — this brings the shared runtime to parity, plus marketplaceApi.installPackage, which had the identical hole and could report a package as installed when it was not.

Current servers answer a failed action with a real HTTP status, which !res.ok catches first. The inner-envelope check is what keeps the console honest against a runtime that has not been upgraded yet — worth keeping, not a transitional shim.

Second defect this surfaced

With objectstack#3913 the failure body is {success: false, error: {message, code}}. RecordDetailView read json?.error raw:

const errMsg = (innerFailed && inner.error) || json?.error || `Action "${targetName}" failed (HTTP ${res.status})`;

That hands an object to toast.error() as a React child and crashes the page (React #31) — the exact failure useConsoleActionRuntime's local errorDetail helper was written to prevent. The helper is now a shared util (utils/actionErrorDetail) and both call sites go through it, so a nested {message} always resolves to a string.

Testing

• Full app-shell suite: 1918 passed (232 files).
• type-check clean; eslint 0 errors on the changed files.
• 3 new cases in useConsoleActionRuntime.test.tsx: the inner-success:false failure, the nested {error:{message}} → string resolution, and a success guard so the new check can't turn a good action into a failure.
• Verified the inner-envelope test is meaningful: with the || innerFailed guard removed it fails, and passes with it.

🤖 Generated with Claude Code

https://claude.ai/code/session_011AvZj6cLX7APd7roh2eK4F

Generated by Claude Code